Measures for estimating effort of incremental integration software testing

According to experts, incremental integration testing is the best solution to perform two lowest levels of testing software developed through procedural paradigm: unit and integration testing. This paper introduces two measures for estimating effort of an incremental integration testing task during software development: the estimated number of tests and the number of units. The measures are introduced in the context of a specially developed methodology for planning and tracking incremental integration testing. The formulas for these measures are given and the motivation for specifying these formulas is explained. The advantage of these measures is that they can be directly derived from software design and used in the effort estimation and cost prediction. The first experimental results on a number of programs written in C verify that the proposed measures can be used for estimating effort of incremental integration testing.International Conference on Computer, Communication and Control Technologies (CCCT 03)/9th International Conference on Information Systems Analysis and Synthesis (ISAS03), Proceedings, Jul 31-Aug 02, 2003, Orlando, F

The cost of the managed and unmanaged incremental integration software testing

This paper studies incremental integration testing from the management point of view for software developed through procedural paradigm. It considers the managed, planned and tracked, incremental integration testing. The advantage of the managed way of testing is the fact that testing becomes visible when the managed way is performed. This visibility enables us to see the process of testing in detail and thus contributes to better testing. The aim is to determine the cost of the managed incremental integration testing measured as the actual effort spent on this testing and compare it with the cost of the unmanaged testing. The cost determination has three steps. First, the managed incremental integration testing is completely and precisely defined. Second, this managed incremental integration testing is applied to the development of a number of programs and the data on testing are collected. Third, based upon these data the cost of the managed and unmanaged incremental integration testing are computed and compared. The analysis shows that the cost of the managed incremental integration testing is greater than the cost of the unmanaged testing of approximately 23%. Without this quantitative analysis, the comparison between the managed and unmanaged way of testing can be just qualitative and thus vague.International Conference on Cybernetics and Information Technologies, Systems and Applications/10th International Conference on Information Systems Analysis and Synthesis, Proceedings, Jul 21-25, 2004, Orlando, F

Measures for estimating effort of incremental integration software testing

According to experts, incremental integration testing is the best solution to perform two lowest levels of testing software developed through procedural paradigm: unit and integration testing. This paper introduces two measures for estimating effort of an incremental integration testing task during software development: the estimated number of tests and the number of units. The measures are introduced in the context of a specially developed methodology for planning and tracking incremental integration testing. The formulas for these measures are given and the motivation for specifying these formulas is explained. The advantage of these measures is that they can be directly derived from software design and used in the effort estimation and cost prediction. The first experimental results on a number of programs written in C verify that the proposed measures can be used for estimating effort of incremental integration testing.International Conference on Computer, Communication and Control Technologies (CCCT 03)/9th International Conference on Information Systems Analysis and Synthesis (ISAS03), Proceedings, Jul 31-Aug 02, 2003, Orlando, F